Update libgsystem

And while we're here, also update the TODO slightly.

diff --git a/TODO b/TODO
index e84ea953791754523f42c411a5f6360a5ed91508..4d6f2add2aa7d35577e828009601fe0ddc7b4361 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,16 +1,8 @@
 * Documentation
   - More gtk-doc
 
-* Rethink commit objects
-  - Drop the a{sv} per https://bugzilla.gnome.org/show_bug.cgi?id=673012
-  - Do we need freeform subject/body?  Or should it just be a generic
-    key-value store?
-  - Optional non-object metadata; e.g., "detached" GPG signatures which
-    are in the same file (to avoid double HTTP requests)
-  - Extended validation; SHA512+SHA256 checksum of all metadata along
-    with content object metadata (file size in particular) wouldn't take
-    too much extra time per commit, and would greatly strengthen resistance
-    to active hash collision attacks.
+* Local metadata packs
+  - Just to avoid lots of little files on each client
 
 * Hybrid SSL pull (fetch refs over SSL, content via plain HTTP)
 
@@ -28,6 +20,11 @@
   Chromium autoupdate: set of operations to perform given previous
   object set to create new objects.
 
+* Flexible "prune" that allows keeping only a rolling subset of history.
+  For example, keep the last week, keep at least 1 build a week up
+  till a year ago, then 1 build a month, etc.  Optionally rewrite commit
+  parent history?
+
 * Tests of corrupted repositories, more error conditions
 
 * Structured output from commandline?  ostree --output={table,gvariant} ?

diff --git a/src/libgsystem b/src/libgsystem
index bd2c1e436b270b39ca262765e775b4556d6bd50b..c72d84a0a9edcccb366ba41b74e7a41a6d625ab1 160000 (submodule)
--- a/src/libgsystem
+++ b/src/libgsystem
@@ -1 +1 @@
-Subproject commit bd2c1e436b270b39ca262765e775b4556d6bd50b
+Subproject commit c72d84a0a9edcccb366ba41b74e7a41a6d625ab1